Large quantities of data travel through the measurement system, both at the device level where it is measured and collected, at the station level where it is reported out for various production enterprise uses, and within the system itself where it is calculated, evaluated, and processed to arrive at the best possible record values. Components of the data handling process include the following.
See CygNet Measurement Data Calculation for more information about how calculations are performed.
Request data by sending FMS commands via FMS Explorer, CygNet Explorer, ActiveX controls on CygNet Studio/Vision screens, or scripting.
See FMS Commands and Running Node Commands for more information about data request commands.
See Device Data and Station Data in the CygNet Measurement Concepts section for information about understanding levels of FMS data.
See FMS Explorer for more information about the CygNet Measurement user interface.
Import data into and export data from CygNet Measurement via the FMS service, using a variety of methods, to fulfill specific business requirements.
Data can be brought into CygNet Measurement by executing commands against device Nodes, by executing file import commands, or by using the CygNet FMS Toolbox utility.
Node Commands allow you to configure and run commands against FMS device Nodes to retrieve device data. See Running Node Commands and Using the Commands Menu for more information.
System Commands can be used to configure and run file import commands for file types that have been registered on your system. See Running File Import Commands and Using the Commands Menu for more information.
The CygNet FMS Toolbox utility helps you to migrate data from a GMR database into FMS, or to import data via a definition or template file from another FMS database into your FMS system. See FMS Utilities for more information.
Data can be sent out from CygNet Measurement by executing system commands against selected Nodes, by exporting data directly from FMS Explorer controls, or by running scheduled or ad hoc reports.
System Commands can be used to configure and run commands to export several types of files from your system. See Running File Export Commands and Using the Commands Menu for more information.
Note: Some system commands used for data export, such as Device Data CSV and Completed Jobs, are not available through FMS Explorer but can be accessed via scripting or the MSS in CygNet Explorer. See FMS Commands for more information.
Node Commands can be used to export raw data to Flow-Cal in a variety of format options, if installed on your system and configured to do so. See Managing Node Commands and Using the Commands Menu for more information.
FMS Explorer controls can be used to export data directly from the controls via .csv files. See Using the Controls Menu and the control toolbar for each control for more information.
The History Graph control can be used to export graphical data in a variety of formats. See Exporting History Graphs for more information.
The Reports control can be used to export data in report form, either on a scheduled or ad hoc basis. See Running FMS Reports for more information.
The CygNet FMS Toolbox utility can be used to help you export FMS devices out of the CygNet Measurement system via .csv files for editing before import back into FMS. See FMS Utilities for more information.
Validation is a method of ensuring that values entering the CygNet Measurement system are of acceptable accuracy so that calculated values will provide the best possible measurement data. Validation engines and rules can be set up to automatically validate the accuracy of all incoming data and optionally, if configured to do so, to validate the accuracy of edited data. When data fails validation, exceptions can be generated if configured to do so. Validation functionality is available in systems licensed for either FULL or REPOSITORY modes.
See Validation in the CygNet Measurement Concepts section, and Managing Validation Engines for more information.
Exceptions provide a method of handling data values that failed validation when entering the CygNet Measurement system. Exception handling functionality is available in systems licensed for either FULL or REPOSITORY modes.
See Exceptions in the CygNet Measurement Concepts section, and Using the Exceptions Control for more information.
Estimation is a method of providing better values when collected data is missing, of low quality, or late. Estimation engines and rules can be set up to automatically handle estimating values for missing data and data of low quality, and estimation commands can be created and executed to handle estimating values for late data.
See Estimation in the CygNet Measurement Concepts section, and Managing Estimation Engines for more information.
Normalization of data provides for uniform display and comparison of station-level data values, and occurs automatically at multiple points within the CygNet Measurement system. Normalization also occurs to support uniformly rolling up records for export or reporting out of CygNet Measurement. Various normalization "views" can be defined to provide a unified format for the presentation of data collected under varying conditions, and referenced for communication and reporting purposes to produce records meeting a variety of business requirements.
See Normalization of Data and Normalization Views in the CygNet Measurement Concepts section, and Configuring Normalization Views for more information.
Analysts access large quantities of data and edit the values to arrive at the best possible records. The main vehicle for editing CygNet Measurement data is the History Grid control in FMS Explorer. Edits can also be made to the data contained in the Alarm log and Configuration log controls.
The Save button 
is made available on the History Grid, Alarm, and Configuration controls when edits are made, and can be used to save your edits directly from the controls where you are editing. Any changes made to a record after the period has been closed may generate a prior period adjustment.
See Using the History Grid Control, Using the Alarm Control, and Using the Configuration Control for more information.
Once issues with the data are properly resolved, data can be tested (optionally) and the record period can be closed. When records are closed, an audit entry is created in the system and the best (closed) records can be distributed to downstream users of the data, such as production accounting. Any future changes to previously closed periods may generate a prior period adjustment, which would then need to be handled in the system.
See Using the Close Period Control and Testing and Closing Periods for more information.
Once the best possible values have been determined and the station records have been closed, data may still come into the system. In this circumstance, a prior period adjustment (PPA) may be generated. Once PPA records exist, they must either be approved or rejected for export to downstream users of the data, to alert them to any data modifications.
See Using the Prior Period Adjustment Control for more information.
Optionally move device data records from the FMS database to an offline archive file location once records are older than a specified period of time by executing an Archive Data system command. Using this option makes more space available in your FMS database, while preserving access to the archived data.
See Archiving CygNet Measurement Data and Archive Data for more information.
|
|
|
